Known issues

Known issues in Kanzi Engine

• Kanzi Engine ignores the Format property of textures and treats all textures as if the value of the Format property was Automatic.
• Some parts of Kanzi API are written in C. In the future Kanzi releases we will continue the effort of converting the API to C++.
• When linking applications to the libraries provided with SDK without sources generates warning about missing debug information.
• Because Nexus 7 (2012, 1st generation) device does not support bilinear filtering of half-float textures, the Post_Processing example does not work on that device.
• Clipping of rotated child 2D nodes is ignored because of performance reasons. For example, if an Image node has a child Image node, and you rotate the child Image node, the parent Image node does not clip the child Image node.
• Current limitation of the Kanzi Engine is that if a 2D node is forced to render to a render target (for example, Viewport 2D with rotation), clipping is applied even when you disable clipping in a 2D node.
• A bug in V8 causes a memory leak the size of a pointer. If you do not use scripting in your Kanzi application, you can remove the V8 library.
• When you change the Samples property of a Render Target Texture you have to restart the Preview to apply the change.
• When the glyph cache texture in Kanzi Studio is full, the application performance decreases in Kanzi Studio. This does not affect the performance of your Kanzi application when you build it and appropriately adjust the size of the glyph cache texture for your target platform. See Glyph cache texture size.
• Rendering text with a font that does not use a well-defined baseline can cause Kanzi to render that text at incorrect line height.
• The Node2D_plugin example prints warnings when you run it in the Preview.
• The render passes do not support these features which will be included in the future releases of Kanzi:
  • Cubemap render target textures
  • Multiple render targets

  To achieve these rendering results, except the cubemap render target textures, use the Legacy Render Pass (deprecated).

• Kanzi application freezes when user scrolls a Trajectory List Box 3D with negative item spacing absolute value of which is higher than the width of list box items.
• Setting the recognition threshold for the pinch gesture using the PinchManipulator::setScaleRecognitionThreshold and PinchManipulator::setRotationRecognitionThreshold functions does not work.

Known issues in Kanzi Studio

• Kanzi installer fails to install VC++ 2017 x64 redistributable if you have already installed it on top of VC++ 2015 x64 or x86 redistributable.
  Workaround: Manually run the VC++ 2017 x64 redistributable installer and select to the option to repair the installation. The easiest way to do this is to run the Add or Remove Programs, click modify next to the VC++ 2017 x64 redistributable, and then repair.
• When you import the same dds file twice, Kanzi Studio creates an invalid texture and shows invalid content in the Image property dropdown menus.
  Workaround: Update the file in Windows Explorer, or delete the dds file and its texture before importing them again.
• The device driver for the AMD Radeon R9 M370X included in the Boot Camp update 6.0 causes the Preview to not work. To fix the issue, use the Windows Device Manager to roll back to the previous version of the driver.
• Importing fbx files which contain animations that use custom pivot points, can cause Kanzi Studio to terminate. This is caused by a defect in the FBX importer provided in the Autodesk's FBX SDK.
  

  After the import fails, open the Kanzi Studio project:

  1. In the Library > Resource Files > 3D Assets select the fbx file that caused Kanzi Studio to terminate.
  2. In the Properties disable the Convert Pivot Points property.
     
     When disabled, Kanzi Studio ignores the custom pivot points in the fbx file, which can affect the rotation and scale animations for nodes that use custom pivot points.
     When enabled, Kanzi Studio resets the pivot points to the default positions without making visual changes to animations. This is the recommended setting because Kanzi Studio does not support custom pivot points.
     Custom pivot points contain an additional transform which Kanzi Studio bakes into a single transform. In some cases, custom pivot points do not contain any data, so disabling this option does not affect the content.
  3. In the Library > Resource Files > 3D Assets right-click the fbx file that caused Kanzi Studio to terminate, and select Import 3D Asset File to import the file.
     
  
  
• Kanzi Studio does not support importing of animated pivot points.
• OpenGL ES (IMG) graphics API is not stable enough to be used for development. Use the IMG graphics API only for testing. For content development use the OpenGL. Set the Default Preview OpenGL ES Wrapper in the Edit > User Preferences > Advanced > Default Preview OpenGL ES Wrapper.
• When you run Kanzi Studio in Parallels or VMWare Fusion, the IMG Preview OpenGL ES Wrapper does not work because of a bug in the IMG wrapper.
  Workaround: Use the GL wrapper.
• Kanzi Studio is compatible only with screen DPI settings set to 100%.
• When you close the Project window, the selection in the window does not update correctly.
• Thumbnails are not rendered correctly for all assets.
• Copy-pasting in the Project a Scene prefab that contains a skinned mesh does not work.
  Workaround: Drag and drop the Scene prefab from the Prefabs to the location in your project where you want to use it.
• When you use the keyboard to move the free camera in the Preview, the Camera tool Reset Camera command does not correctly reset the camera.
  Workaround: Use the mouse to rotate the camera and then use the Reset Camera command in the Preview.
• When you reload the changes from a referenced Kanzi Studio project that is opened in another instance of Kanzi Studio, Kanzi Studio can become unstable.
  Workaround: Close the referenced project before you reload the changes in the project where the project is referenced.
• Kanzi Build Environment sometimes fails to download SCons from the address available for automatic download.
  Workaround: Manually install the Kanzi Build Environment. See Installing the Kanzi build environment manually.
• The Direct routing mode for message triggers does not work.
• When a node contains multiple instances of the same prefab, you cannot create a binding from the node that contains these prefabs to the properties of nodes inside an instance of that prefab.
  Workaround: Make the properties to which you want to bind available in the root of the prefab and create the bindings in the root of the prefab instance. See Customizing instances of a prefab.
• When you create a node, Kanzi Studio sometimes prints a warning to the Log window.
• In the Localization RTL tutorial when in the Kanzi Studio Preview you click the buttons to change the locale, Kanzi Studio prints a warning to the Log.

Known issues in the Kanzi SDK

• When you open a Kanzi application in Visual Studio 2015 and you select to upgrade the Visual Studio 2013 configurations to 2015, the configurations do not work anymore.
  Workaround: Do not upgrade the configurations to Visual Studio 2015.
• Building your Kanzi application on Windows can fail when the path is longer than 260 characters.
  Workaround: If you are using Windows 10, to remove this limitation, edit the Windows registry. See https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/

Known issues on platforms

• When you use QNX 7.0.0 and update your QNX software through the QNX Software Center, the compilation of Kanzi applications fails with error

  Kanzi-3_6_5-qnx700_screen_aarch64-es3-freetype-static/Engine/include/kanzi/core/cpp/cstdio.hpp:42:12: error: 'std::snprintf' has not been declared

  QNX introduced this error in an update of their software development platform where the std::snprintf is missing in header files.
  Workaround: To remove the compilation error, add to the preprocessor flags the -DKZ_USE_C99_SNPRINTF definition.

See also

Release notes and migration guides

Open topic with navigation